Skip to content

Conversation

@zixlin7
Copy link
Contributor

@zixlin7 zixlin7 commented Mar 18, 2025

Problem

Solution

Basic paginated inline suggestions implementation using language server (related: aws/language-servers#831)


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

@zixlin7 zixlin7 changed the title feat(amazonq): basic paginated suggestions using flare feat(amazonq): basic paginated suggestions using language server Mar 18, 2025
@zixlin7 zixlin7 force-pushed the pagination branch 2 times, most recently from 76d917b to ba33860 Compare March 18, 2025 16:51
@zixlin7 zixlin7 marked this pull request as ready for review March 19, 2025 00:36
@zixlin7 zixlin7 requested a review from a team as a code owner March 19, 2025 00:36
const swapProviderAndShow = async () => {
await commands.executeCommand('editor.action.inlineSuggest.hide')
this.disposable.dispose()
this.disposable = languages.registerInlineCompletionItemProvider(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this still have the weird effect where the number of items shown in the inline completion don't get updated? I guess thats unavoidable though?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes it still has that issue and it's not avoidable unfortunately

@zixlin7 zixlin7 requested a review from jpinkney-aws March 20, 2025 22:57
@jpinkney-aws
Copy link
Contributor

In terms of merging this, do we have to do it after the inline changes are released from the language servers side? Or can we do it now and it won't break anything?

@zixlin7
Copy link
Contributor Author

zixlin7 commented Mar 21, 2025

/retryBuilds

@jpinkney-aws jpinkney-aws deleted the branch aws:master March 21, 2025 21:37
@jpinkney-aws jpinkney-aws reopened this Mar 21, 2025
@jpinkney-aws jpinkney-aws changed the base branch from feature/amazonqLSP to master March 21, 2025 21:41
@jpinkney-aws jpinkney-aws merged commit e01574f into aws:master Mar 24, 2025
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants